I am not sure how the data processing works there. can we get that message on the transaction list? where we have the "description" ? cc @rolznz

Yes we can, but we have to discuss on the priority order
For example boostagram > keysend message > description

Yes we can, but we have to discuss on the priority order
For example boostagram > keysend message > description

Sounds good (and the description would be empty in this case I think anyway)

but we would need to persist that data in the DB. we should not on the fly always decode those keysends.

that's why we have the DB. prepare the data as our app needs it.

@bumi @im-adithya I think we should go with Bumi's recommendation, right?

@im-adithya would you like to propose the changes you would make? or how should we proceed here?

TODOs

• Fix/Add tests
• Store proper description (boostagram > keysend message > description) in db

Example queries:

SELECT *
FROM transactions
WHERE EXISTS (
    SELECT 1
    FROM json_each(metadata, '$.tlv_records') AS records
    WHERE json_extract(records.value, '$.type') = 7629169
);

SELECT *
FROM transactions
WHERE json_extract(boostagram, '$.value_msat') > 1000;

Roland's tests (WIP):

• migration with transactions with both metadata and no metadata
• query of metadata from migrated transactions
• query of metadata from new transactions
• querying boostagrams
• send boostagram
• receive boostagram
• view boostagram info - sent
• view boostagram info - receive
• NIP-47 lookup invoice / list transactions / notifications returns correct content